Looks kinda nice, even with that strange
energy-thing going on...

And thanks for the stats. In effect, giving
that you rendered 10 times as many frames
as needed, one could say the parsing per
actual frame of animation is 40 seconds.
For 60 balls in a box, and with just that energy
problem, but no balls falling out, I'd say
thats kinda good coding. OTOH, as soon
as trace() is brought in, I'll expect it to
go higher, as you'll need more than just one
trace per ball.
Once you do have object interaction, try
something new: instead of using balls, use
blobs, and try to simulate water with,
don't know, 300 to 500 spheres. Have it
poured out of a bucket or such.
You'd have to switch off rotations for that,
although that might still be a nice special
effect for the water...

Oh, and do your particles support different
sized particles, or do they have to be the
same size?

-- 
Tim Nikias v2.0
Homepage: http://www.digitaltwilight.de/no_lights
Email: no_lights (@) digitaltwilight.de


> Looks like I have another bug.  I threw in 60 balls into the box (note:
> front panel is invisible) but my physics system couldn't handle the
> pressure.  Sudden burst of (accumulated?) energy are released.  I have a
> few ideas why and I think I can address the problem.  Not permitting
> slippage doesn't help.  I'm also thinking that having to write out all of
> the float values to a text file between frames sure doesn't help data
> precision either (I've increased the output length).  Still the results
> are kind of funny.
>
> Stats for Tim ;-):
>
> Simulation time: 10 seconds
> Rendered 2400 frames averaged down to 240 for motion blur...
> On an Athlon 1.2Ghz
>
> Time For Parse/Frame:    0 hours  0 minutes   3.9 seconds (3 seconds)
> Time For Parse Total:    2 hours 34 minutes  28.0 seconds (9268 seconds)
> Time For Trace/Frame:    0 hours  0 minutes   0.5 seconds (0 seconds)
> Time For Trace Total:    0 hours 19 minutes   5.0 seconds (1145 seconds)
>           Total Time:    2 hours 53 minutes  33.0 seconds (10413 seconds)
> -------------------------------------------------------------------------
> CPU time used: kernel 2579.92 seconds, user 10753.82 seconds, total
> 13333.74 seconds
> Render averaged 1.44 PPS over 19200 pixels
>
>

Post a reply to this message